[infra] Run cuNLS tests in PR CI - #167
vikuznetsov-nvidia wants to merge 3 commits into
Conversation
|
Navigate logical layers of code changes, visualize relationships, and explore their blast radius. No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository: nvidia-isaac/cuVSLAM/.coderabbit.yaml Review profile: ASSERTIVE Plan: Enterprise Run ID: 📒 Files selected for processing (3)
Included review availability: This review used your included allowance. Your plan provides up to 12 included reviews per hour; 11 remain after this review. 📝 WalkthroughWalkthroughThe build system adds an opt-in cuNLS test option. cuNLS uses a pinned commit, preserves the caller’s testing state, and configures required test settings. Two source files update cuNLS factor-header includes. The x86_64, Orin, and Thor verification jobs enable the option. ChangescuNLS Test Enablement
Priority: ⬇️ Low Estimated code review effort: 2 (Simple) | ~10 minutes Change: Other Merge Risk: ⚪ Minimal · up to The three verification jobs enable and run the cuNLS tests, and the updated headers resolve against the pinned dependency. No merge-blocking risk was identified. 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches 💡 1📝 Generate docstrings
🧪 Generate unit tests (beta)
🛠️ Fix failing CI checks 💡
Comment |
Test Results
Failed testsThor / C++:
Artifacts |
TEST
Summary by CodeRabbit
Tests
Chores